-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nav Unification: Update masterbar #45467
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~23 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Legend What is parsed and gzip size?Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
0bd0783
to
31e5dbe
Compare
Deployed r213505-wpcom |
3685cea
to
5dab1d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work @frontdevde ! Especially the comments with the source files will be really useful!
I just added a box-shadow to the whole masterbar (as it appears in wp-admin).
Tested by test instructions and desktop viewports are identical when combined with D49342-code!
Mobile breakpoints are very close to wp-admin, let's figure out the menu and finalise them in an other PR.
LGTM!
Changes proposed in this Pull Request
This is PR is a first step towards implementing the changes to the masterbar suggested in #45393.
Screenshots
Current PR state compared to wp-admin (in code-D49342):
Notes
This is a prototype and it's hidden behind a feature flag. We'll continue iterating on it.
As the prototype uses an additional class for scoping some styles of other masterbar states like support session and jetpack will be overridden due to the increased specificity. This is expected for this prototype.
When Calypso loads you'll see an initial flash of the app shell with the old nav styles. This is because we're using a feature flag to attach a class to the layout that gets processed once the client side JS kicks in. Once we move the styles to be the default, the app shell will look like the unified masterbar.
Testing instructions
This is behind a feature flag so we can iterate on it. Testing should mainly ensure something isn't fundamentally broken.
yarn && yarn start
, visit isit http://calypso.localhost:3000/, add?flags=nav-unification
to the end of the URL to see changes